home *** CD-ROM | disk | FTP | other *** search
Text File | 1996-01-20 | 70.4 KB | 2,245 lines |
-
-
- FDInt 1.00 Documentation ───────────────────────────────────────────────────────
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- FDInt 1.00
- (c) 1995 Colin Turner & Chris McCandless,
- All Rights Reserved.
-
- Documentation by Colin Turner.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- - 1 -
-
-
-
-
- FDInt 1.00 Documentation ───────────────────────────────────────────────────────
-
-
-
-
- Warranty
- ════════
-
- You know the form, there is no warranty. If you're nervous I strongly
- recommend experimenting after a backup or leaving the program alone. Neither
- I, Colin Turner, nor Chris McCandless can be held accountable for any damage
- incurred through the use of FDInt.
-
- For example, just suppose one of your users writes a message about setting up
- a BBS to a user on another board, and suppose that FDInt intercepted this
- message and readdressed it to the senile American president in office at the
- time of reading, and this message had become so garbled as to contain the
- american nuclear launch codes followed by a rude note apparently from the
- drunken russian president currently in office. Just suppose, that in a fit of
- rage, said U.S. president authorises a nuclear strike on Russia, and that
- Russia retaliates, laying most of the globe to waste. And suppose that an
- alien race which has been watching the earth for years decides to use this
- opportunity to colonise the earth and subjugate it to millenia of autocratic
- rule. Now suppose that the human race throws off these oppresors and evolves
- a law system again, not even then are we legally liable. Get the picture?
-
- Distribution Information
- ════════════════════════
-
- FDInt refers to the executables FDINT.EXE, FDINTBIG.EXE and FDISETUP.EXE along
- with all associated documentation. All copyrights are retained by Colin Turner
- & Chris McCandless for FDInt. No fee may be charged for the distribution of
- FDInt, except to cover reasonable costs. Additionally, all the files in the
- original archive must be distributed intact and unchanged. Other files may not
- be added.
-
- Legal Status
- ════════════
-
- Version 1.00 of FDInt comes in two flavours, the Freeware version, and the
- registered Shareware version. This is somewhat unusual, as these two versions
- are both contained in the executable FDINT.EXE (or FDINTBIG.EXE, which is
- functionally the same as FDINT.EXE but which is compiled in the compact
- memory model making more memory available to large setups, but with a small
- decrease in speed (probably most noticeable on 386 SX or below processors)).
-
- Think of it as having a shareware program with an unlimited evaluation period.
- You are free to use the program in it's unregistered form indefinitely, and
- quite legally. In it's freeware form FDInt will only support two mailing lists
- and the listserv module will be entirely inactive (so you must manually add
- and remove users from lists).
-
- If at any point you decide you would like to use the extra features, you can
- simply fill in the attached REGISTER.FRM and post it along with the small fee
- and you will be sent a unique registration key allowing you access to the
- better features.
-
-
-
-
-
- - 2 -
-
-
-
-
- FDInt 1.00 Documentation ───────────────────────────────────────────────────────
-
-
-
- Contents
- ════════
-
- 1. Installation .............................................. 7
- 1.1 Where to place the files .................................. 7
- 1.2 Previous users of FDInt ................................... 7
- 1.3 Running FDISetup .......................................... 7
- 1.4 Batch File Installation ................................... 7
- 1.5 Registration keys ......................................... 8
- 1.6 Running the program ....................................... 8
-
- 2. Configuration ............................................. 9
- 2.1 Basic Configuration ....................................... 9
- 2.1.1 Paths ..................................................... 9
- 2.1.1.1 Editor Path & Name ........................................ 9
- 2.1.1.2 Semaphores ................................................ 10
- 2.1.2 Time Zone Kludge .......................................... 10
- 2.1.3 Semaphore Time ............................................ 10
- 2.1.4 Split Length .............................................. 10
- 2.1.5 Origin Line ............................................... 10
- 2.1.6 System Attributes ......................................... 11
- 2.1.6.1 Delete Original ........................................... 11
- 2.1.6.2 Delete Reply .............................................. 11
- 2.1.6.3 Preserve File Attaches .................................... 11
- 2.1.6.4 Change destination ........................................ 11
- 2.1.6.5 Fake origin ............................................... 11
- 2.1.6.6 Readdress messages ........................................ 11
- 2.1.6.7 History File .............................................. 12
- 2.1.6.8 List Format ............................................... 12
- 2.1.7 Message Attributes ........................................ 13
- 2.1.8 Address setup ............................................. 13
- 2.1.8.1 Gate Name ................................................. 13
- 2.1.8.2 Gate Address .............................................. 13
- 2.1.8.3 Echo Address .............................................. 13
- 2.2 Names and Commands menu ................................... 14
- 2.2.1 Domain names .............................................. 14
- 2.2.2 Server names .............................................. 14
- 2.2.3 ListServer names .......................................... 14
- 2.2.4 Various Commands .......................................... 14
- 2.2.4.1 Command Summary ........................................... 15
- 2.2.5 Groups .................................................... 15
- 2.3 Document Manager .......................................... 16
- 2.4 List Manager .............................................. 17
- 2.4.1 Overview of lists ......................................... 17
- 2.4.2 Linking EchoMail with Mailing Lists [ * Technical * ] ..... 17
- 2.4.3 Setting up a mailing list ................................. 18
- 2.4.3.1 Setting up mailing list users ............................. 19
- 2.5 Template Manager .......................................... 20
- 2.6 Redirection Manager ....................................... 21
- 2.7 History Viewer ............................................ 21
-
- 3. Command line parameters ................................... 22
- 3.1 FDInt command line parameters ............................. 22
- 3.2 FDISetup command line parameters .......................... 23
-
-
-
- - 3 -
-
-
-
-
- FDInt 1.00 Documentation ───────────────────────────────────────────────────────
-
-
- 4. Errorlevels ............................................... 24
-
- 5. Examples of How to Use FDInt .............................. 25
- 5.1 File Requests For Points .................................. 25
- 5.2 Making Routing of Email Easier ............................ 25
- 5.3 Email from a BBS, more easily ............................. 25
- 5.4 Allowing your points to write in echoes when away ......... 25
- 5.5 Making a technical support area ........................... 25
-
- 6. Instructions for the End User ............................. 27
- * Document Server ........................................... 27
- * UUCP readdressing - only relevant to FTN users ............ 28
- * Mailing Lists ............................................. 28
- * List Server ............................................... 29
-
- 7. Frequently Asked Questions ................................ 31
-
- 8. Notes ..................................................... 33
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- - 4 -
-
-
-
-
- FDInt 1.00 Documentation ───────────────────────────────────────────────────────
-
-
-
- Overview
- ════════
-
- I initially started FDInt as a set of InterNet utilities for FrontDoor Sysops
- who have access to a UUCP address which uses REPLYADDR kludges. However, as
- it is also designed to reply and act on FidoNet Technology Network (hereafter
- FTN) mail, it is quite useful to other FrontDoor sysops.
-
- Therefore the program is really a set of utilities which are "InterNet gate
- aware".
-
- Current Feature List
- ════════════════════
-
- * All supplied executables detect and time slice under the following multi
- taskers : Desqview, MicroSoft Windows, OS/2.
-
- * A full document server. Messages can be written to FDInt as a number of
- aliases which will post back documents (through gates or to other FTN
- addresses). It is possible to password protect documents.
-
- * Messages addressed to UUCP at one of your addresses can be automatically
- redirected to your InterNet gate. This means your points don't have to
- cope with changes of address, you need only change the gate address in the
- config file.
-
- * Messages addressed to a username containing an "@" character to one of your
- AKAs can be rewritten to the gate. This allows you and your points to
- write messages directly "to" the InterNet address of the recipient.
-
- * A function for hosting mailing lists, with both InterNet and FTN members.
- Hosting more than 2 lists requires a valid registration key.
-
- * <+> ListServer functions for automatic subscription to and from lists. It
- also allows remote users to survey the lists you offer on your system.
-
- * The ability to link mailing lists to FTN EchoMail conferences, thereby
- allowing InterNet and remote FTN users to participate in the echo is if it
- were a mailing list at their end.
-
- * The ability to redirect netmails arriving for users at your address to
- other nodes, points or InterNet addresses.
-
- * A setup utility, FDISETUP.EXE written for that very familiar feel.
-
- * Automatic upgrading of your old setup files by FDISetup.
-
-
-
-
-
-
-
-
-
-
-
- - 5 -
-
-
-
-
- FDInt 1.00 Documentation ───────────────────────────────────────────────────────
-
-
-
- Operational Information
- ═══════════════════════
-
- FDInt has been tested for versions of FrontDoor 2.02, 2.12, 2.20. In addition
- a new version will be forthcoming after the release of the next version of
- FrontDoor.
-
- You will probably require DOS version 3.XX or above if you want to be able to
- run FDInt without first changing into it's directory. FDInt will handle most
- environments including local area networks, as it uses full file sharing modes
- to access both its own files and those of FrontDoor etc.
-
- A note to Network users. FDInt uses semaphores and logic to determine which
- messages it should open. This is what makes the scanning so quick. However, if
- your network machines have clocks that are out of sync, you will find that
- messages may get missed or scanned repeatedly. You should always ensure that
- your client clocks are regularly synchronised. (A good time is after every
- inbound call.) As a last resort use the /FULLSCAN command line parameter.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- - 6 -
-
-
-
-
- FDInt 1.00 Documentation ───────────────────────────────────────────────────────
-
-
-
- 1. Installation
- ═══════════════
-
- 1.1 Where to place the files
-
- Place the files FDINT.EXE and FDISETUP.EXE programs in a directory which
- you are able to write to at runtime. FDInt will store all its configuration
- files in this directory automatically, regardless of what path you are in
- when you run FDInt or FDISetup. If you wish to use the Compact memory
- version of FDINT.EXE you may rename FDINTBIG.EXE to FDINT.EXE.
-
- 1.2 Previous users of FDInt
-
- If you are a previous user of FDInt, it is recommended that you survey the
- WHATSNEW file included in this archive. Depending on what versions you are
- upgrading from and to, you may find FDInt will not run on your existing
- configuration. You need not worry, FDInt won't do anything if it feels the
- setup files are for the wrong version. Instead you will be told to run
- FDISETUP.EXE, which will automatically upgrade your setup for you. (Note
- however, it may be sensible to make sure all new features are configured
- as you want them, though FDISetup will try to use sensible defaults where
- possible).
-
- 1.3 Running FDISetup
-
- You should now run FDISetup and follow the instructions in section 2 on
- configuration before returning here.
-
- When you quit FDISETUP you should now have all the files needed to run
- FDInt.
-
- SETUP.FDI Essential, basic configuration.
- DOCLIST.FDI Required for Document Server.
- MAILLIST.FDI Required for Mailing lists.
- REDIRECT.FDI Required for redirecting mail from name on your system.
- TEMPLATE.FDI Some response files used in the program.
- TAG.ML A file for each mailing list tag detailing the users.
-
- Which of these files are present will often depend on how you configure your
- system. For example, if you do not use the list manager, there will be no
- MAILLIST.FDI.
-
- 1.4 Batch File Installation
-
- You should now install FDInt in your batch file, for example :
-
- =-=-=-= Cut
-
- :Inbound
- REM Inbound mail
- GEcho Toss
- C:\BBS\FDINT\FDInt
- GEcho Import Pack
-
- =-=-=-=
-
-
- - 7 -
-
-
-
-
- FDInt 1.00 Documentation ───────────────────────────────────────────────────────
-
-
-
- Note that FDInt is run before GEcho Import, as at this stage all the netmail
- that has just come in is in the *.MSG FD Netmail folder which FDInt scans.
-
- If you are gating echomail, you should probably run it after outbound scans
- as well. Don't worry, typically FDInt takes about a second to work out that
- there is nothing to do if that's the case.
-
- =-=-=-= Cut
-
- :OutBound
- REM Outbound mail
- GEcho Scan
- C:\BBS\FDINT\FDInt
- GEcho Pack
-
- =-=-=-=
-
- 1.5 Registration Keys
-
- If you have a reg key, ensure it is called FDINT.KEY and is in the same
- directory as FDINT.EXE. Note that the reg key must be registered to the
- first username is SETUP.FD and that user must be a supervisor. Any error
- will result in FDInt running in unregistered mode.
-
- It is possible to request a demo key from 2:443/13.0 or 2:443/14.0 under
- the name FDIKEY. This will give you an expiring key with a life of 30 days,
- so you can try out the registered features. This key will be particular to
- your system, and it goes without saying, subsequent requests for a key from
- that system will be denied.
-
- 1.6 Running the program
-
- You are now ready to run the program for the first time. You may see a lot
- of messages scroll past and the first run may be quite lengthy. After each
- run, FDInt will touch a semaphore called LASTSCAN.NET which it will keep in
- the same directory as FDINT.EXE. When FDInt is run subsequent times it will
- only examine messages that are newer than this stamp, increasing the scan
- speed dramatically.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- - 8 -
-
-
-
-
- FDInt 1.00 Documentation ───────────────────────────────────────────────────────
-
-
-
- 2. Configuration
- ════════════════
-
- FDInt takes its configuration information from your FrontDoor System files
- as well as from it's own custom files. FDISETUP.EXE should be run to create
- and edit your FDInt configuration. FDISetup is compiled in the large memory
- model and so will allow you to create large configurations that may not be
- loadable in full by the small version of FDInt. When you run FDISetup and
- create your new setup, you should see the following menu.
-
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒┌─────────────── Main ┐▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ │▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ Basic Configuration │▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ Names and Commands │▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ Document Manager │▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ List Manager │▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ Template Manager │▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ Redirection Manager │▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ History Viewer │▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ Information │▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ Quit │▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒└─────────────────────┘▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
-
- 2.1 Basic Configuration
-
- You should now go through all the options on the Basic Configuration menu.
- Simply use the cursor keys to move the highlight bar over this entry and
- hit return. (To return from such a menu, use Escape).
-
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒┌─────────────────────┐▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ ┌ Basic Configuration ┐▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ Bas│ │▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ Nam│ Paths │▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ Doc│ Time Zone │▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ Lis│ Semaphore Time │▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ Tem│ Split Length │▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ Red│ Origin Line │▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ Inf│ System Attributes │▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ Qui│ Message Attributes │▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ │ Address Setup │▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒└────│ │▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒└─────────────────────┘▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
-
- 2.1.1 Paths
-
- This will in turn pop up a small submenu allowing you to edit the following
- paths.
-
- 2.1.1.1 Editor path & name
-
- In this field you can specify the name and path to your favourite DOS ASCII
-
-
- - 9 -
-
-
-
-
- FDInt 1.00 Documentation ───────────────────────────────────────────────────────
-
-
- file editor. This will allow you to edit most documents inside FDISETUP.
-
- You should type the usual parameters you would use in here, using a ~F to
- indicate where the filename should go. So for example
-
- EDIT ~F
-
- would call DOS's native Editor with the textfile loaded.
-
- 2.1.1.2 Semaphores
-
- You can use this field to define semaphores you wish FDInt to create in
- particular situations. If a filename without a path is specified the file
- will be created in the semaphore directory as defined by FrontDoor. You may
- wish to create a specific semaphore to control FrontDoor (see FD.DOC) or
- you may specify a name of your own to control with an "IF EXIST".
-
- You can include environment variables in these filenames by enclosing them
- in the notation $[VAR]. So for example
-
- FDXIT$[TASK].201
-
- will drop a semaphore FDXIT2.201 on a system where TASK is defined as 2.
-
- The toss semaphore will be dropped when FDInt creates a new FDINT???.PKT
- file (this may happen if you are gating EchoMail), which you will probably
- want to toss as soon as possible.
-
- The scan semaphore will be dropped when FDInt unpacks a PKT that was
- destined to it, you could use this to pack the netmails that may result.
-
- 2.1.2 Time Zone Kludge
-
- The via kludge lines inserted by FDInt should have 3 characters on the end
- to denote what time zone you are in. This defaults to UTC (GMT) but you
- should change this to whatever timezone string is used where you live.
-
- 2.1.3 Semaphore Time
-
- When FDInt encounters a FrontDoor busy semaphore it will wait, checking
- once every second to see if the semaphore has cleared. If it has to wait
- longer than the value specified here in seconds, it will abort (and do
- nothing).
-
- 2.1.4 Split length
-
- When FDInt is sending large documents in the document server it will split
- them at intervals specified here. The default is 16, which means that FDInt
- will post the file in 16K chunks.
-
- 2.1.5 Origin Line
-
- This origin line will be appended to NetMail or Email being forwarded into
- an FTN echomail conference. Please see the mailing list section for more
- details.
-
-
-
- - 10 -
-
-
-
-
- FDInt 1.00 Documentation ───────────────────────────────────────────────────────
-
-
- 2.1.6 System Attributes
-
- This function calls up the following submenu.
-
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ ┌─────────────────────┐▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ Bas┌──────────── System Attributes ┐▒▒▒▒▒▒▒▒▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ Nam│ │▒▒▒▒▒▒▒▒▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ Doc│ Delete Original Yes │▒▒▒▒▒▒▒▒▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ Lis│ Delete Reply Yes │▒▒▒▒▒▒▒▒▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ Tem│ Preserve File Att. Yes │▒▒▒▒▒▒▒▒▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ Red│ Change Destination Yes │▒▒▒▒▒▒▒▒▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ Inf│ Fake origin No │▒▒▒▒▒▒▒▒▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ Qui│ Readdress Messages Yes │▒▒▒▒▒▒▒▒▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ │ History File Yes │▒▒▒▒▒▒▒▒▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒└────│ List format list%user@ │▒▒▒▒▒▒▒▒▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ │▒▒▒▒▒▒▒▒▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒└───────────────────────────────┘▒▒▒▒▒▒▒▒▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
-
- 2.1.6.1 Delete Original
-
- When a message addressed to the listserv, docserve or other module is
- replied to the original will be deleted if this is enabled. If not, the
- message will simply be marked as received. This also applies to redirected
- mail.
-
- 2.1.6.2 Delete Reply
-
- Selecting this attribute causes FDInt to mark it's outgoing mail as "Kill",
- so that after being sent by the mailer or packed they will be deleted from
- your netmail folder.
-
- 2.1.6.3 Preserve File Attaches
-
- When a NetMail with a file attach is redirected, or exploded into a list,
- the file attach will be honoured to all FTN NetMail receivers, Otherwise
- the file attach will be removed.
-
- 2.1.6.4 Change destination
-
- If a netmail addressed to UUCP at one of your AKAs is found, and this is
- enabled, FDInt will readdress it to your FidoNet <=>InterNet gate. This
- allows your points, or other software, not to worry about where your gate
- is, in case it should move at a later date.
-
- 2.1.6.5 Fake origin
-
- If a netmail comes through the system which is processed by either the
- "Change destination" above, or the "Readdress message" below and this is
- enabled. FDInt will make it appear that the message came from your AKA.
- This is to allow tidy addresses for your points.
-
- 2.1.6.6 Readdress messages
-
- If a netmail addressed to one of your AKAs is found, with an "@" character
- in the to field, and this switch is on, then FDInt will address it to the
-
-
- - 11 -
-
-
-
-
- FDInt 1.00 Documentation ───────────────────────────────────────────────────────
-
-
- correct program (usually UUCP) at the gate address, with the To: line in
- the first text line. Again, this allows downlinks to post more easily to
- the InterNet.
-
- 2.1.6.7 History File
-
- This switch dictates whether or not FDInt will create a HISTORY.FDI file
- during runtime which it uses to record its actions (in a binary banner for
- reading by other utilities as opposed the the log which is designed to be
- read by humans).
-
- 2.1.6.8 List Format
-
- This decides the default format for messages addressed to lists. You can
- choose between the format
-
- list@machine.name
-
- or
-
- list%user@machine.name
-
- The former will mean that only mail received to the list name exactly will
- be exploded and can be used in case of difficulty. The latter still allows
- messages addressed to list@machine.name which will be directed to all, but
- in addition, it will accept the more advanced format allowing messages to
- be written to a specific user on the list. For example
-
- remote%colin.turner@thog.conqueror.co.uk
-
- will result in a message being exploded in the list remote, but with the
- extra information that it was addressed to colin turner in particular.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- - 12 -
-
-
-
-
- FDInt 1.00 Documentation ───────────────────────────────────────────────────────
-
-
-
- 2.1.7 Message Attributes
-
- Choosing this option calls up the following submenu.
-
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ Lis│ Semaphore Time │▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒┌─ Attributes ┐ength │▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ │Line │▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ Hold Off │Attributes │▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ Direct Off │ Attributes │▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ Crash Off │ Setup │▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ │ │▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒└─────────────┘─────────────┘▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
-
- Mail being redirected to the gate will be given these attributes. Use with
- extreme care.
-
- 2.1.8 Address setup
-
- Again, this provides a submenu.
-
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ Red│ Origin Line │▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒┌─── Addresses ┐Attributes │▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ │ Attributes │▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ Gate Name │ Setup │▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ Gate Address │ │▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ Echo Address │─────────────┘▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ │▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒└──────────────┘▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
-
- 2.1.8.1 Gate Name
-
- This is the name of the program gated mail should be posted to, usually
- this is UUCP.
-
- 2.1.8.2 Gate Address
-
- This is the FTN address of your FidoNet <=> InterNet gateway. Often this
- is a point of your midnight line or other mail uplink.
-
- 2.1.8.3 Echo Address
-
- This FTN address is used for gating EchoMail backwards and forwards to
- mailing lists. It MUST NOT be one of your AKAs, or for that matter the AKA
- of any actual system. I recommend you choose a point number of your own
- system, and use it. Then add a DENY <Address> command to your ROUTE.FD to
- prevent anyone polling using that AKA (or stick a password for it in the
- security manager in FDSetup.) Please see the mailing list section later.
-
-
-
-
-
-
-
-
- - 13 -
-
-
-
-
- FDInt 1.00 Documentation ───────────────────────────────────────────────────────
-
-
-
- 2.2 Names and Commands menu
-
- Going back to the main menu and selected Names brings up the following.
-
- ─────────────────────────────────────────────────────────────────────
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒┌─────────── Names ┐▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ │▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ Domain Names │▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒┌───│ Server Names │▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ │ Listserver Names │▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ Ba│ Subscribe │▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ Na│ Unsubscribe │▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ Do│ List commands │▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ Li│ Help commands │▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ Te│ Send commands │▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ Re│ Member commands │▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ In│ Pause commands │▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ Qu│ Resume commands │▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ │ Echo commands │▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒└───│ Groups │▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ │▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒└──────────────────┘▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
-
- 2.2.1 Domain names
-
- This allows you to tell FDInt what machine name your system has, for example
- in my case it is thog.conqueror.co.uk. In short this is your address, after
- the "@" character.
-
- 2.2.2 Server names
-
- The server name menu selects the names which the document server will
- respond to. For example, if you choose FDINT, then FDInt will respond to
- messages addressed to
-
- fdint@thog.conqueror.co.uk, if your domain name is thog.conqueror.co.uk.
-
- or messages addressed to fdint and one of your FTN addresses. Note that
- these names are case insensitive. To disable the document server, simply
- blank all these names.
-
- 2.2.3 ListServer names
-
- <+> The listserv names will only be responded to in the registered version.
- In that version the listserv can be used to automatically connect and
- disconnect from lists and requests a list of lists. Please see Section 6
- for details of how the end user can work it.
-
- 2.2.4 Various Commands
-
- You may now configure the words that FDInt will accept as command words for
- various doument and list server functions. In each case you can have up to
- five different commands to trigger the functions. Blanking all these strings
- will disable the function in question.
-
-
- - 14 -
-
-
-
-
- FDInt 1.00 Documentation ───────────────────────────────────────────────────────
-
-
-
- Spacing in these strings can be used and is significant. If, for example,
- you define a string as simply "+" then
-
- +tag
-
- will trigger the action, on the other hand, if the string is "SUB ", then
-
- SUBtag
-
- will not trigger the action whereas
-
- SUB tag
- SUB tag
-
- will all trigger the function. Note that FDInt is case insensitive when
- comparing these commands.
-
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ Na│ Unsubscribe │▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ Do│ List commands ┌──────── Subscribe ┐▒▒▒▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ Li│ Help commands │ │▒▒▒▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ Te│ Send commands │ 1 SUBSCRIBE │▒▒▒▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ Re│ Member commands │ 2 SUB │▒▒▒▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ In│ Pause commands │ 3 + │▒▒▒▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ Qu│ Resume commands │ 4 │▒▒▒▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ │ Echo commands │ 5 │▒▒▒▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒└───│ Groups │ │▒▒▒▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ └───────────────────┘▒▒▒▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒└──────────────────┘▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
-
- 2.2.4.1 Command Summary
-
- I now give a brief description of each command purpose.
-
- Subscribe Used by listserv to hook up mailing lists;
- Unsubscribe Used by listserv to unhook mailing lists;
- List Used by listserv and document server, provides a list of
- available lists / documents;
- Send Used by document server, mainly for password protected
- documents;
- Member Used by listserv to get a list of members on a list;
- Pause Used by listserv to temporarily pause flow from a list;
- Resume Used by listserv, opposite of Pause;
- Echo Used by listserv, allows users to subscribe to a list while
- being marked as non active and connected via an echo. This is
- only to allow echo users to appear in member lists.
-
- 2.2.5 Groups
-
- It is possible to arrange the documents into up to ten groups. Here you
- define the names of some or all of the groups.
-
-
-
-
-
-
-
- - 15 -
-
-
-
-
- FDInt 1.00 Documentation ───────────────────────────────────────────────────────
-
-
-
- 2.3 Document Manager
-
- The Document Manager can now be setup. Note that you'll need at least one
- entry in the server name list to trigger this function. Hitting return
- over the Document server bar allows you to get the following:
-
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ │▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
- ▒┌─ View 3/26 ──────────────────────────────────────────── Document Manager ┐▒
- ▒│ │▒
- ▒│ Tag BBS1 Times requested 4 │▒
- ▒│ Description The BBS Basics, what to look for │▒
- ▒│ Password │▒
- ▒│ Invisible No │▒
- ▒│ Group FidoNet related │▒
- ▒│ Path Y:\FILES\I&CT\BBS1.TXT │▒
- ▒│ │▒
- ▒└──────────────────────────────────────────────────────────────────────────┘▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
-
- Although this is in fact a filled in item. To enter items, hit Insert. The
-
- Tag is the word that is used on the subject line to request;
- Description is for your own use, and also for the generated lists;
- Password is to protect the document against casual requests;
- Invisible dictates whether the document appears on a list request;
- Path is the textfile to send.
-
- To request documents from your system, a user should send a message to the
- server (see above), with document tags on the subject line, separated by
- spaces. However, another method, using the send command allows a password
- to be passed for those files that require it. Usage is detailed elsewhere.
-
- Pressing space will result in any editor you previously configured in
- 2.1.1.1 allowing you to edit the document text without leaving FDISetup.
-
- The group is picked from the list you defined in 2.2.5.
-
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
- ▒▒┌───────────────────────────────────────────────────────── Groups ┐▒▒
- ▒▒│ │▒▒
- ▒▒│ 0 General documents │▒▒
- ──│ 1 InterNet related │──
- │ 2 FidoNet related │
- g │ 3 FDInt, this program │
- sc│ 4 │
- ss│ 5 │
- ou│ 6 │
- th│ 7 │
- │ 8 │
- ──│ 9 │──
- ▒▒│ │▒▒
- ▒▒└─────────────────────────────────────────────────────────────────┘▒▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
-
- This will be used partially for your own benefit, but also in generated
-
-
- - 16 -
-
-
-
-
- FDInt 1.00 Documentation ───────────────────────────────────────────────────────
-
-
- lists of documents requested.
-
- It is possible to configure two different tags to match the same filename,
- giving a popular name an alias to make it easier to request.
-
- The document server does not naturally search for the help commands, but,
- it is a simple matter to create a document with the tag "Help", and in case,
- there is a template sent in the event of an error which could contain this
- information (see Templates in 2.5).
-
- The times requested field is non editable, and is updated if you use a
- binary history file, and periodically run FDISETUP /UPDATE.
-
- 2.4 List Manager
-
- You are now ready to setup mailing lists if you wish. The unregistered
- version only supports 2 lists, the registered is limited only by memory.
-
- 2.4.1 Overview of lists
-
- A mailing list is a dud username at your system. When a message is posted
- to such an address it is exploded to a list of people. Each message appears
- to come from the fake address, so a reply will cause another explosion etc.
-
- FDInt will handle lists with both InterNet and FTN users as well as users
- in a given FTN EchoMail Conference. If you are going to use the facility to
- link mailing lists to echoes, read the next section, otherwise, skip on.
-
- Please ensure that you comply with policy and behave responsibly in your
- routing of mail.
-
- 2.4.2 Linking EchoMail with Mailing Lists [ * Technical * ]
-
- To link EchoMail conferences to lists it is vitally important that you
- correctly configure your echomail processor. You will need a processor
- which can create and unpack type 2+ PKT files. Almost all modern ones do.
-
- First of all you should decide on an address to use for gating (see the
- notes above, echo address). You should then set that address up in your
- echomail processors node manager. Again, please note, this address MUST
- *NOT* be one of your AKAs.
-
- Ensure that the archiving method for this node is set to none. ie. PKT.
- Otherwise FDInt will ignore the attach. Don't pack netmail to this AKA
- (it won't crash FDInt, it will simply ignore it, so if you can't avoid it
- it's no big problem).
-
- Now simply add this address to the connection lists of echoes you wish to
- link to mailing lists, and set up the list as outlined in the following
- information.
-
- For those of you that are curious. When FDInt wishes to send a message to
- an EchoMail conference, it creates a FDINT???.PKT file in your FrontDoor
- inbound files directory, where your mail processor will toss it into the
- correct area(s). In the other direction, FDInt scans the netmail folder
- for attaches to it's fake echo address, when it finds one it unpacks it
-
-
- - 17 -
-
-
-
-
- FDInt 1.00 Documentation ───────────────────────────────────────────────────────
-
-
- to the mailing lists.
-
- 2.4.3 Setting up a mailing list
-
- As usual, pressing Insert allows you to create a new list.
-
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
- ▒┌─ View 1/8 ───────────────────────────────────────────────── List Manager ┐▒
- ▒│ │▒
- ▒│ Tag BRS │▒
- ▒│ Description Old pupils of Bangor R School, friends and teachers. │▒
- ▒│ Password │▒
- ▒│ Echo Tag BRS │▒
- ▒│ Connected Yes │▒
- ▒│ List Access Anyone can write in the mailing-list │▒
- ▒│ Serv Access Subscription can be performed by listserv │▒
- ▒│ Invisible No │▒
- ▒│ Read Only No │▒
- ▒│ Banner No Banner will be placed on echomail messages │▒
- ▒│ List format list%user@ │▒
- ▒│ Members │▒
- ▒│ │▒
- ▒└──────────────────────────────────────────────────────────────────────────┘▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
-
- Where the :
-
- Tag is the name of the dummy user, ensure it's not a real user;
- Description is a short description of the purpose of the list;
- Password protects the list from casual subscription, a remote user
- must send this password with the subscription attempt to be
- allowed onto the list;
- Echo Tag is the Echo Tag this is connected to if need be;
- Connected dictates whether the Echo is connected at this time;
- List Access dictates if people not on the list post to it;
- Serv Access dictates if people can automatically subscribe <+>;
- Invisible dictates if list is hidden when a user requests a list? <+>;
- Read Only means only Owners of the list can post into it;
- Banner will prevent an information banner being added to echomail
- gated from this list <+>;
-
- so in the above example, brs can be written to at
-
- brs@thog.conqueror.co.uk (the domain name being added again)
-
- or at brs at one of your AKAs.
-
-
-
-
-
-
-
-
-
-
-
-
- - 18 -
-
-
-
-
- FDInt 1.00 Documentation ───────────────────────────────────────────────────────
-
-
-
- 2.4.3.1 Setting up mailing list users
-
- Hitting RETURN over Members allows you to add, alter or remove users from
- the list. Note that users may also be altered by the listserver if this is
- enabled <+> for this list.
-
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
- ▒┌─ View 3/11 ──────────────────────────────────────────────── Member Lists ┐▒
- ▒│ │▒
- ▒│ Name Colin Turner │▒
- ▒│ Address Type Fido Technology │▒
- ▒│ Address 2:443/13.0 │▒
- ▒│ User Type Normal │▒
- ▒│ Active Yes │▒
- ▒│ │▒
- ▒└──────────────────────────────────────────────────────────────────────────┘▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
-
- You can easily create entries to either FidoNet or InterNet addresses. User
- Type is either normal or owner. Owners can still write to read only lists,
- and please note that multiple owners of a list are possible. Output from a
- list can be paused for a particular user by labelling them as non active.
-
- The records should be sorted in alphabetical order, although elements added
- automatically by the listserv module may be out of sequence. This problem
- will solve itself the next time you insert or delete a record, or if you
- run FDISETUP /PACK.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- - 19 -
-
-
-
-
- FDInt 1.00 Documentation ───────────────────────────────────────────────────────
-
-
-
- 2.5 Template Manager
-
- The template system gives you some control over the output creates by FDInt.
- It is possible to specify text which will be placed into messages in various
- places.
-
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ │▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
- ▒┌──────────────────────────────────────────────────────── Template Manager ┐▒
- ▒│ │▒
- ▒│ Description Inserted before a list of documents │▒
- ▒│ Text / File File │▒
- ▒│ Data M:\FDINT\INSERT\DOCLIST.TXT │▒
- ▒│ │▒
- ▒└──────────────────────────────────────────────────────────────────────────┘▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ Quit │▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
-
- You can traverse the standard prompts using the left and right arrow keys as
- usual. The description should tell you what the purpose of a particular
- template is, or when it is used. If you have only a very small amount of
- text to add, simply select Text and then type the text into the data field.
- However, frequently you may want to send more information, and in these
- cases select file and give the pathname of a textfile for the purpose. You
- can, as for the document manager, edit this file from inside FDISetup by
- pressing space if an editor is correctly configured as in 2.1.1.1.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- - 20 -
-
-
-
-
- FDInt 1.00 Documentation ───────────────────────────────────────────────────────
-
-
-
- 2.6 Redirection Manager
-
- It is possible to configure FDInt to redirect mail to certain names on your
- system to other Fido Style, or InterNet addresses.
-
- Simply insert a record in the redirect manager. This is very similar in its
- functionality to the list member manager. This will be the address the mail
- will be redirected to. Then, press RETURN over the Psuedonames field.
-
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ │▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
- ▒┌──────────────────────────────────────────────────────────────────────────┐▒
- ▒│ │▒
- ▒│ Name Chris McCandless │▒
- ▒│ Address Type Fidonet Technology │▒
- ▒│ Address 2┌──────────────────────────── Pseudonames ┐ │▒
- ▒│ Pseudonames │ │ │▒
- ▒│ │ 1 Chris McCandless │ │▒
- ▒└───────────────│ 2 cpm │────────────────┘▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ 3 │▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ 4 │▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ 5 │▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ │▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒└─────────────────────────────────────────┘▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
-
- This pops up another box in which you can configure up to 5 names for which
- mail at your system will be redirected. This is ideal for sending netmail
- for points that has arrived at your node address to their point address.
-
- 2.7 History Viewer
-
- FDInt can generate a file called HISTORY.FDI as it runs. This is in effect
- a binary log file, and is mainly designed to be read by other programs such
- as FDISetup itself (which will read it to update document request pointers).
-
- You can of course use the log text file generated in order to see what FDInt
- has been doing, but in addition, you can analyse the History file using the
- viewer built into FDInt. Note that it is not possible to edit the History
- file contents using this, and in addition the file is accessed on the disc
- as opposed to being read into memory first.
-
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ │▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
- ▒┌─ View 26/27 ────────────────────────────────────────────── History Viewer ┐▒
- ▒│ │▒
- ▒│ Action Document Request; Success │▒
- ▒│ Time 00:06:21 AM ; 06 December, 1995. │▒
- ▒│ Tag bbs2 │▒
- ▒│ User name Colin Turner │▒
- ▒│ Address type Fidonet Technology │▒
- ▒│ Address 2:443/13.0 │▒
- ▒│ │▒
- ▒└───────────────────────────────────────────────────────────────────────────┘▒
- ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
-
-
-
-
- - 21 -
-
-
-
-
- FDInt 1.00 Documentation ───────────────────────────────────────────────────────
-
-
-
- 3. Command line parameters
- ══════════════════════════
-
- 3.1 FDInt command line parameters
-
- FDInt will probably run quite well without command line parameters at all. It
- will attempt to locate your SETUP.FD, so make sure you have defined the FD
- environment variable or left SETUP.FD in the current directory. However, the
- following command line parameters are supported.
-
- /LOG:<filename>
-
- This, rather unsurprisingly produces a log of the activity. The log file is
- in FrontDoor style. Leaving this parameter out stops the creation of a log
- file at all.
-
- /DEBUG:<Debug Level>
-
- For more information, you can place this, and a debug level between 1 and 9.
- Simply placing /DEBUG on its own assumes maximum debug information.
-
- /BIOS
-
- Disables direct video which is enabled by default.
-
- /C
-
- Override colour mode. Selects colour mode. (See below)
-
- /M
-
- Override colour mode. Selects monochrome mode. (See below).
-
- /SILENT
-
- At certain points FDInt may beep to warn you of some configuration problem,
- this could be due to the fact that documents have incorrect paths, or you
- are running unregistered and trying to use more than two lists.
-
- /FULLSCAN
-
- Forces FDInt to scan the whole netmail folder regardless of what it thinks
- are new messages. This will slow the scanning and should only be used if
- you have severe clock problems you can't otherwise solve. However, it may
- be wise to run FDInt with this parameter in your maintenance cycle once a
- day in case of small clock problems.
-
- A note about the colour selection. FDInt will select the same colour mode as
- you have chosen for FDSETUP by default. Therefore on a multiline system with
- some colour and some monochrome lines, you should be able to use no parameter
- at all to get the required behaviour.
-
- If you are running multiline, FDInt will read and use your TASK environment
- variable, so make sure it is correct.
-
-
-
- - 22 -
-
-
-
-
- FDInt 1.00 Documentation ───────────────────────────────────────────────────────
-
-
- 3.2 FDISetup command line parameters
-
- FDISetup has the following command line parameters
-
- /M
- /C
-
- These work in the same way as for FDInt, the default is read from SETUP.FD
- if possible.
-
- /PACK
-
- When you use FDISetup to view, create and delete entries, in the various
- managers, they should be maintained in alphabetical order, as FDISetup sorts
- them into order as it loads them from disk. However, if a record is added by
- the listserver or another program, it will not be in order, and although
- later work in FDISetup will place the record in order you may wish to
- automatically reorder the files. (FDINT.EXE does not sort the entries for
- speed reasons, and sorted entries make for more cosmetic lists).
-
- This parameter causes FDISetup to load, sort and save the files DOCLIST.FDI,
- MAILLIST.FDI, REDIRECT.FDI and the .ML files.
-
- /UPDATE
-
- If you use a HISTORY.FDI file, FDISetup will scan it for document requests
- and update the request counters for each document in turn.
-
- /PURGE:<Days>
-
- This command purges your HISTORY.FDI, deleting entries older then the given
- number of days, the default is 30.
-
- All but /M and /C are therefore to be used in your maintenance cycle rather
- than in normal operation. It is possible to use more than one mode at a
- time. For example
-
- FDISETUP /PACK /UPDATE /PURGE
-
- will do all your maintenance in one go, and notice that the order of the
- parameters is irrelevant, FDISetup will always proceed in the logical order.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- - 23 -
-
-
-
-
- FDInt 1.00 Documentation ───────────────────────────────────────────────────────
-
-
-
- 4. Errorlevels
- ══════════════
-
- FDInt will exit with the following errorlevels.
-
- 0 Nothing to do.
- 1 Error opening SETUP.FDI file.
- 2 Error opening or reading FrontDoor setup file.
- -
- 10 New messages created.
- 11 Busy semaphores still there after 30 seconds.
- -
- 20 Error opening Debug Log file.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- - 24 -
-
-
-
-
- FDInt 1.00 Documentation ───────────────────────────────────────────────────────
-
-
-
- 5. Examples of How to Use FDInt
- ═══════════════════════════════
-
- FDInt is a versatile tool and can be used in many various ways. In the
- course of writing this program, our Beta test team often found ways of using
- the we hadn't even considered, and so we'd be interested to hear from you
- if you use FDInt for a purpose we haven't thought of. Here, however, we will
- outline some of the things FDInt can do.
-
- 5.1 File Requests For Points
-
- FDInt allows points to specify all their favourite text files to be made
- available to anybody who can netmail them (or mail from the InterNet through
- a gate).
-
- We'd ask points to be responsible and ask their Bosses for permission for
- doing this though. FDInt will even split large documents if required.
-
- You'll find all the information you need under the "Document Server" section
- of the manual.
-
- 5.2 Making Routing of Email Easier
-
- Many FrontDoor sysops now have access to some sort of InterNet gating. FDInt
- is (and was in fact primarily) designed to reply happily to mail from such
- gates. It can also make it easier for people to send mail. Tell all your
- points / users / software that they can send InterNet mail to your FTN
- address and let FDInt redirect it to the gate for them. If you change gate,
- you only have to change one option to be working business as usual.
-
- 5.3 Email from a BBS, more easily
-
- Many programs, like RemoteAccess are difficult to set up so users can use
- your gate without frequent mistakes. Not anymore. Simply tell RemoteAccess
- to automatically send a netmail to one of your AKAs, and allow the user to
- place the InterNet address on the to line as they would expect, and let
- FDInt do the rest. It will redirect the message to the correct program, that
- is, normally UUCP at the gate address, and place the correct To: line on the
- start of the message. You can switch this feature on and off in FDInt at
- will.
-
- 5.4 Allowing your points to write in echoes when away from home
-
- Suppose you have a popular point echo, and one of your points goes away to
- university and doesn't have Fido access (life's not worth living ;-)). All
- you need to do is create a mailing list and attach it to your echo (you can
- read the details in FDINT.DOC). Now, every time your friend uses his free
- university InterNet account to mail your list, FDInt will not only mail any
- other people on the list, but import the message to the echo. Likewise, all
- mail in the echo will be directed outwards to members on the list.
-
- 5.5 Making a technical support area
-
- Perhaps you too develop software? Create a mailing list called "support",
- and attach it to an echo. Make the list Public, but Closed. Now connect all
-
-
- - 25 -
-
-
-
-
- FDInt 1.00 Documentation ───────────────────────────────────────────────────────
-
-
- your technical people to the list (either via the echo, or netmail, or
- email, any or all are possible). Now no-one can connect themselves to the
- list as it is Closed, but anyone can post to it. So a message addressed to
- support@blah.blah or support at your FTN address will go to all your tech
- crew who can talk it over privately in the list before replying via netmail
- or email.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- - 26 -
-
-
-
-
- FDInt 1.00 Documentation ───────────────────────────────────────────────────────
-
-
-
- 6. Instructions for the End User
- ════════════════════════════════
-
- We recommend that you cut this section out and modify it to your needs, and
- then make it available to users of FDInt at your system.
-
- Instructions for use of FDInt 1.00
- ==================================
-
- FDInt provides 4 basic services. You should contact your sysop for details of
- which services are offered at his site.
-
-
- * Document Server
-
- FDInt has the ability to act as a document server. In other words, you can
- post requests for textfiles to it, and it will post them back to you in the
- body of a message. You should ask your sysop what document server names are
- defined. Usually, it will be "docserv" or similar. Each document will have
- a short tag, which you can use to request it. Asking for "list" will give
- you all available tags.
-
- _________________________________________________________________________
-
- To use the document server from a Fido Technology Network (FTN) address :
-
- Post a message with the following form :
-
- To: docserv <server name, see above>
- At: FTN address of system <any AKA will do>
- Re: Document list <Seperate document tags with spaces>
-
- for example, if fdint is running at 2:443/13.0
-
- To: docserv
- At: 2:443/13.0
- Re: bbs1 list help info
-
- Will result in up to 4 documents being posted back to you, including a list
- of all available documents.
-
- *** NOTE *** You may have to put some text in the message body. FDInt 1.00
- ignores this, but without it, some programs will delete the message.
-
- _________________________________________________________________________
-
- To use the document server from an InterNet address :
-
- You will need to know the domain name of the system running fdint. Your
- message should then be addressed
-
- To: docserv@domain <server@domain.name>
- Re: (as above)
-
- so it could be for example:
-
-
- - 27 -
-
-
-
-
- FDInt 1.00 Documentation ───────────────────────────────────────────────────────
-
-
-
- To: docserv@thog.conquer.co.uk
- Re: bbs1 list info help
-
-
- * UUCP readdressing - only relevant to FTN users
-
- FDInt has the ability to make InterNet addressing easier for it's users.
-
- When sending mail to the InterNet from an FTN address, the format is usually
- as follows :
-
- To: UUCP
- At: <Gate address>
- Re:
-
- and the message body reads
- To: <InterNet address>
-
- text...
-
- FDInt provides a way for your sysop to simplify this. Please check which of
- these options is enabled. (Possibly both).
-
- 1) Readdressing of messages to UUCP.
-
- In this mode, the message is addressed as above, but the At:, Fido address
- will be any of the AKAs of your sysops system. FDInt will then rewrite this
- message to the gate. This removes the need for you to remember the gate
- address, and indeed, for all intents and purposes, your sysops system is the
- gate.
-
- 2) Readdressing of mail containing a "@" in the To:
-
- In this mode, mail addressed to one your sysops AKAs with a "@" in the To:
- address. For example, you could address your message like this :
-
- To: Joe@blah.domain
- At: <AKA of your sysop>
- Re: as normal
-
- and FDInt will automatically readdress this to UUCP at the gate as detailed
- above. This will greatly simplify addressing.
-
-
- * Mailing Lists
-
- This function allows your sysop to host mailing lists at their system. A
- mailing list is essentialy a fake address (in that it does not point to
- any one person). When a message is written to the fake address it will be
- exploded to each person on the list. The mailing lists can have members on
- both the InterNet and FTNs. Each mailing list has a tag, much as in the
- document server.
-
- _________________________________________________________________________
-
-
-
- - 28 -
-
-
-
-
- FDInt 1.00 Documentation ───────────────────────────────────────────────────────
-
-
- Posting to a mailing list from an FTN address:
-
- To: <The unique tag of the mailing list>
- At: <any AKA of FDInt's system>
-
- eg. for a mailing list with a tag "test"
-
- To: test
- At: 2:443/13.0
-
- _________________________________________________________________________
-
- Posting to a mailing list from an InterNet address:
-
- To: tag@domain <The tag is the username, you must specify the domain>
-
-
- Lists can be set to Private on the FDInt system, in which case you may not
- post to them unless you are on them.
-
- When the message is exploded, it will appear to come from the name of the
- list, so a simple reply will reply to the list name, and consequently be
- exploded again.
-
-
- * List Server
-
- FDInt, (in it's registered version) provides a way of automatically adding
- and removing yourself from existing lists.
-
- Your sysop will have setup a name for this feature, the most common is
- "listserv". You can request a list of available mailing lists be sending
- a message as below to listserv, with list on the subject line.
-
- _________________________________________________________________________
-
- Subscribing to and unsubsribing from a list from an FTN address.
-
- Write a message of the following form to subscribe to the list with tag
- "test".
-
- To: listserv <Or other name defined by your sysop>
- At: <One of FDInt's addresses>
- Re: subscribe test
-
- Note the subject line is case insensitive.
-
- To unsubscribe, simply place :
-
- Re: unsubscribe test
-
- *** NOTE *** Again, some message text may be required to prevent your
- message being deleted.
-
- _________________________________________________________________________
-
-
-
- - 29 -
-
-
-
-
- FDInt 1.00 Documentation ───────────────────────────────────────────────────────
-
-
- Subscribing to and unsubscribing from a list from an InterNet address.
-
- Write a message of the following form to subsribe to the list with tag
- "test".
-
- To: listserv@domain <domain is the site name for FDInt>
- Re: subsribe test
-
- Note the subject line is case insensitive.
-
- To unsubscribe, simply place :
-
- Re: unsubscribe test
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- - 30 -
-
-
-
-
- FDInt 1.00 Documentation ───────────────────────────────────────────────────────
-
-
-
- 7. Frequently Asked Questions
- ═════════════════════════════
-
- Here are a few common queries about FDInt answered.
-
- Q. What's the difference between FDINT.EXE and FDINTBIG.EXE?
-
- A. FDINT.EXE is compiled in the small memory model. This means that only
- one segment (64K) is used for data. However, the pointers used for such
- data are only 16bit in size, and are relatively fast to use. FDINTBIG.EXE
- uses multiple segments (up to whatever remains of your 640K) for data.
- This means that 32bit data pointers are used, so the extra space for
- configuration is paid for in speed. 64K is more than enough for most so
- try FDINT.EXE first.
-
-
- Q. FDInt misses some messages, or scans some over and over again. Why?
-
- A. First of all, when FDInt has processed a message addressed to it, it
- marks it as received (or deletes it) so that it will not perform an
- action on the same message twice. This problem is most often seen in
- LAN (Local Area Network) situations where the various machines on the net
- have slightly different time settings. Try to sychronise clocks more
- frequently, and/or, put an FDINT /FULLSCAN in your nightly maintenance
- cycle to catch any messages you may have missed.
-
-
- Q. FDInt beeps every time it executes and mutters something about a document
- being missing. Why?
-
- A. One of the paths for your documents may be incorrect. FDInt will ignore
- that document on list of document requests, alternatively, you could be
- trying to use more then 2 lists on a unregistered copy. Examine your log
- file closely (even make one for just one run).
-
-
- Q. I'm gating echomail and FDInt keeps trying to reply using the document
- server to echomail PKT files my mail processor creates, why is this?
-
- A. You're probably exporting the echomail to one of your AKAs and have set
- the fake address accordingly, the fake address should NEVER be one of your
- addresses, or the address of any system that may poll you. You should use
- something like a point off your system and use a DENY <address> in your
- ROUTE.FD to prevent the mail being picked up by another system.
-
-
- Q. When I press space in the Document Manager in order to edit a document
- nothing happens, why?
-
- A. Check you have specified an editor to use in editor path, it's also
- possible there isn't enough memory to load it.
-
-
- Q. When I press space in the Document Manager, the editor loads, but empty.
-
-
-
- - 31 -
-
-
-
-
- FDInt 1.00 Documentation ───────────────────────────────────────────────────────
-
-
- A. You have probably ommitted the "~F" in the editor path which is required
- to specify the name of the file you wish to edit.
-
-
- Q. There's a file called HISTORY.FDI which is getting huge, what is it, and
- can I safely delete it?
-
- A. This is a binary history file created as FDInt processes certain tasks,
- if you do not wish to use it you can suppress it's creation by flicking
- the appropriate switch in the system attributes menu in FDISetup. On the
- other hand, you could add a FDISETUP /PURGE:20 command to your batchfile
- in the nightly maintenance which will keep the file's size under control.
-
-
- Q. In the redirection and list member manager, every time I change the type
- of address from Fido to InterNet or back, there is an old address stored,
- is this a bug?
-
- A. No. The file holds information about InterNet and FTN addresses in
- different ways and if there used to be a FidoNet address stored in that
- record it will be reproduced when you change back to it. This can be
- useful for points that have an FTN address at holidays and an InterNet
- address during term time say.
-
-
- Q. People have complained that FDInt didn't reply to their message, I can't
- find a record of the message in the log file either.
-
- A. You may find these are messages from Fido addresses. Many Fido mailers
- will delete messages with no message body, and although FDInt's mail
- robots reply to commands place on the subject line, it may be important
- to place some text in the message body (a sig will do) to prevent the
- message from being nuked.
-
-
- Q. I have been running with mailing lists for some time, but recently they
- have stopped working, the log says something like "no match on tag".
- What can I do to fix this?
-
- A. It could be you changed the echotag of your conference, but it's more
- likely to be a problem with your registration key. If you have more than
- two lists, you need to be registered to use them all, without a key FDInt
- will only load in the first two lists. Perhaps you requested a demo key
- and it had now expired, or your key is not in the same directory as FDInt
- which it should be.
-
-
-
-
-
-
-
-
-
-
-
-
-
- - 32 -
-
-
-
-
- FDInt 1.00 Documentation ───────────────────────────────────────────────────────
-
-
-
- 8. Notes
- ════════
-
- FDInt was written in Turbo 'C++' for DOS 3.0. It also uses a small assembler
- file to determine what multi tasker it is running under and which slicing
- mechanism is used.
-
- The source for FDInt is not available, although, the time slicing code is not
- mine, and is in the public domain, it is available on request, along with the
- C++ header file you will need to use it.
-
-
- Here's a list of people who have contributed something to this program, by
- testing it, making suggestions on how it could be improved or who went out
- to collect the pizzas on the coding nights :-).
-
- Thanks to : Ben Curry, Stephen Glasgow, Joaquim Homrighausen, David Jefferson,
- Mark Kerr, Steve Moore, Scott Myles, Tony Rolt, Mats Wallin,
- Barry Kingston-Wyatt, Craig Young.
-
- Thanks also to Karen, my other half, who put up with being neglected while I
- was busy coding.
-
-
- Future Versions
- ═══════════════
-
- Draft specifications for Version 2 are well under way which should improve on
- this version in many ways.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- - 33 -
-
-
-
-
- FDInt 1.00 Documentation ───────────────────────────────────────────────────────
-
-
-
- Contact addresses & Technical Support
- ═════════════════════════════════════
-
- For technical support write to
-
- support@thog.conqueror.co.uk
- or support at 2:443/13.0
-
- The authors can be reached individually at :
-
- Colin Turner
- ct@thog.conqueror.co.uk
- FidoNet 2:443/13.0; 2:443/14.0
-
- Chris McCandless
- cpm@thog.conqueror.co.uk
- FidoNet 2:443/13.3
-
-
- Demonstration Registration Keys
- ═══════════════════════════════
-
- You can File Request a demonstration key from the above system and try out the
- registered features for up to 30 days. Simply File Request "FDIKEY", the key
- you receive will be tailored for your system.
-
- ══════════════════════════════════════════════════════════════════════════════
-
- Produced and distributed from The Heart Of Gold BBS
-
- +44-1247-274919
- +44-1247-273172
-
- Both lines also support FAX.
-
- ══════════════════════════════════════════════════════════════════════════════
-
- This product has been brought to you by the letter Q and the number 4.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- - 34 -
-
-
-